Methods, systems and apparatus for custom interface specification in a cloud management system

ABSTRACT

Methods, apparatus and articles of manufacture for custom interface specification in a cloud management system are disclosed. An example cloud management system includes: a first interface to communicate with a second interface external to the cloud management system; and a host to manage requests from the second interface and allocate resources to the second interface as a reverse proxy for the second interface with respect to a backend. The example host is to at least: add, at the request of the second interface, an endpoint with respect to the second interface; fetch, at the request of the second interface, data for the endpoint from the backend, the backend identified for the endpoint based on metadata in a component registry; and provide the data from the backend to the second interface.

CROSS-REFERENCE TO RELATED APPLICATIONS

This patent claims priority as a continuation to U.S. Non-Provisionalapplication Ser. No. 16/047,293 entitled “METHODS, SYSTEMS AND APPARATUSFOR CUSTOM INTERFACE SPECIFICATION IN A CLOUD MANAGEMENT SYSTEM” whichwas filed on Jul. 27, 2018, and is hereby incorporated herein byreference in its entirety.

FIELD OF THE DISCLOSURE

The present disclosure relates generally to computing systemvirtualization, and, more particularly, to methods and apparatus forproviding custom interface specification in a cloud management system.

BACKGROUND

Virtualizing computer systems provides benefits such as an ability toexecute multiple computer systems on a single hardware computer,replicating computer systems, moving computer systems among multiplehardware computers, and so forth.

“Infrastructure-as-a-Service” (also commonly referred to as “IaaS”)generally describes a suite of technologies provided by a serviceprovider as an integrated solution to allow for elastic creation of avirtualized, networked, and pooled computing platform (sometimesreferred to as a “cloud computing platform”). Enterprises may use IaaSas a business-internal organizational cloud computing platform(sometimes referred to as a “private cloud”) that gives an applicationdeveloper access to infrastructure resources, such as virtualizedservers, storage, and networking resources. By providing ready access tothe hardware resources required to run an application, the cloudcomputing platform enables developers to build, deploy, and manage thelifecycle of a web application (or any other type of networkedapplication) at a greater scale and at a faster pace than ever before.

IaaS can be provided separate from and/or in conjunction with“software-as-a-service” (SaaS) which provides centrally-hosted software(e.g., hosted on an IaaS, etc.) to users on a subscription basis, suchas using a thin client via a web browser, etc.

Cloud computing environments may include many processing units (e.g.,servers). Other components of a cloud computing environment includestorage devices, networking devices (e.g., switches), etc. Current cloudcomputing environment configuration relies on much manual user input andconfiguration to install, configure, and deploy the components of thecloud computing environment.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 depicts an example system constructed in accordance with theteachings of this disclosure for managing a cloud computing platform.

FIG. 2 illustrates an example generation of a multi-machine blueprint bythe example blueprint manager of FIG. 1.

FIG. 3 illustrates an example installation of deployed virtual machinesand associated servers acting as hosts for deployment of componentservers for a customer.

FIG. 4 illustrates an example implementation of a virtual applianceincluding subscription and provisioning functionality in accordance withthe present disclosure.

FIG. 5 illustrates an example implementation of a virtual appliance toprocess an example blueprint and manage associated subscription(s)according to subscription type, etc.

FIGS. 6A-6B illustrate an example cloud management platform.

FIG. 7 illustrates an example multi-cloud management platform.

FIGS. 8-9 illustrate example data flows in the cloud management platformof FIGS. 6-7.

FIGS. 10-14 depict flowcharts representative of computer readableinstructions that may be executed to implement the cloud managementplatform of FIGS. 1-9.

FIGS. 15-18 are block diagrams of example processing platformsstructured to execute the example computer readable instructions ofFIGS. 10-14 to implement the example systems and flows of FIGS. 1-9.

The figures are not to scale. Wherever possible, the same referencenumbers will be used throughout the drawing(s) and accompanying writtendescription to refer to the same or like parts, elements, etc.

DETAILED DESCRIPTION

Virtualization technologies can be used for computing, storage, and/ornetworking, for example. Using virtualization, hardware computingresources and/or other physical resources can be replicated in software.One or more application programming interfaces (APIs) can be implementedto provide access to virtualized resources for users, applications,and/or systems while limiting or masking underlying software and/orhardware structure.

Cloud computing is based on the deployment of many physical resourcesacross a network, virtualizing the physical resources into virtualresources, and provisioning the virtual resources to perform cloudcomputing services and applications. Example systems for virtualizingcomputer systems are described in U.S. patent application Ser. No.11/903,374, entitled “METHOD AND SYSTEM FOR MANAGING VIRTUAL AND REALMACHINES,” filed Sep. 21, 2007, and granted as U.S. Pat. No. 8,171,485,which is hereby incorporated herein by reference in its entirety.

Cloud computing platforms may provide many powerful capabilities forperforming computing operations. However, taking advantage of thesecomputing capabilities manually may be complex and/or requiresignificant training and/or expertise. Prior techniques to provide cloudcomputing platforms and services often require customers to understanddetails and configurations of hardware and software resources toestablish and configure the cloud computing platform. Methods andapparatus disclosed herein facilitate the management of virtual machineresources in cloud computing platforms.

A virtual machine is a software computer that, like a physical computer,runs an operating system and applications. An operating system installedon a virtual machine is referred to as a guest operating system. Becauseeach virtual machine is an isolated computing environment, virtualmachines (VMs) can be used as desktop or workstation environments, astesting environments, to consolidate server applications, etc. Virtualmachines can run on hosts or clusters. The same host can run a pluralityof VMs, for example.

In certain examples, a VM can host a container and/or a container can beimplemented for virtualization in place of the VM. Containers (e.g.,Docker®, Rocket™ Linux® containers (LXC), etc.) can be used in computingenvironments to run applications, programs, utilities, and/or any othersoftware in isolation. Containers can be used to achieve improvedresource management (e.g., resources used by containerized componentsare isolated for use only by those components that are part of the samecontainer) and/or for security purposes (e.g., restricting access tocontainerized files or components). In addition, containers can also beused to achieve lightweight, reproducible application deployment. Whilea container is intended to run as a well-isolated instance of softwarein a host environment, the security properties of a container imageand/or a container can impact operations of other resources and/orprocesses in a host computer environment in which the containerexecutes.

Prior to running as a container in the host environment, the containeris defined in a container image that specifies components such as anapplication along with any libraries, binaries and/or other files toexecute the container in the host environment (e.g., a VM, etc.). Insome examples, the specified components remain unassembled (e.g., theyare not located together to form a container) until a time at which thecontainer is to be executed. When a determination is made to execute thecontainer in the host environment, the host environment uses thecontainer image to assemble the previously unassembled parts specifiedin the container image for execution as a container. In certainexamples, a platform as a service (PaaS) environment can host aplurality of containers and virtual applications (vApps).

As disclosed herein, methods and apparatus provide for automation ofmanagement tasks such as provisioning multiple virtual machines and/orcontainers for IaaS, SaaS, and/or other product installation. Virtualappliances (e.g., a pre-configured virtual machine image ready to run ona hypervisor, etc.), component servers (e.g., Microsoft Windows™machines, etc.), etc., can be distributed, installed, and managed usingvirtualization of computing resources including operating systemvirtualization.

For example, operating system virtualization (also referred to ascontainer virtualization) can facilitate deployment and management ofvirtual computing resources to provision virtual machines, containers,associated appliances and/or machines, allocate tasks to desired systemsto execute those virtual machines or tasks, and/or reclaim cloudcomputing resources that are no longer in use. The improvements tocloud, cloud-like, and/or other virtual computer/network managementsystems (e.g., the vCloud Automation Center (vCAC) from VMware®, thevRealize Automation (vRA) Cloud Automation Software from VMware®, VMwareNSX® for the Software-Defined Data Center (SDDC), VMware ESXi®enterprise hypervisor, etc.), interfaces, portals, etc., disclosedherein may be utilized individually and/or in any combination. Forexample, all or a subset of the described improvements may be utilized.

As used herein, availability refers to the level of redundancy requiredto provide continuous operation expected for the workload domain. Asused herein, performance refers to the computer processing unit (CPU)operating speeds (e.g., CPU gigahertz (GHz)), memory (e.g., gigabytes(GB) of random access memory (RAM)), mass storage (e.g., GB hard drivedisk (HDD), GB solid state drive (SSD)), and power capabilities of aworkload domain. As used herein, capacity refers to the aggregate numberof resources (e.g., aggregate storage, aggregate CPU, etc.) across allservers associated with a cluster and/or a workload domain. In examplesdisclosed herein, the number of resources (e.g., capacity) for aworkload domain is determined based on the redundancy, the CPU operatingspeed, the memory, the storage, the security, and/or the powerrequirements selected by a user. For example, more resources arerequired for a workload domain as the user-selected requirementsincrease (e.g., higher redundancy, CPU speed, memory, storage, security,and/or power options require more resources than lower redundancy, CPUspeed, memory, storage, security, and/or power options).

In certain examples, when starting up a cloud computing environment oradding resources to an already established cloud computing environment,data center operators struggle to offer cost-effective services whilemaking resources of the infrastructure (e.g., storage hardware,computing hardware, and networking hardware) work together to achievepain-free installation/operation and optimizing the resources forimproved performance. Prior techniques for establishing and maintainingdata centers to provide cloud and/or cloud-like computing services oftenrequire customers to understand details and configurations of hardwareresources to establish workload domains in which to execute customerservices. In certain examples, workload domains are mapped to amanagement cluster deployment (e.g., a vSphere cluster of VMware, Inc.)in a single rack deployment in a manner that is relatively easier tounderstand and operate by users than prior techniques. Thus, asadditional racks are added to a system, cross-rack clusters become anoption. This enables creating more complex configurations for workloaddomains as there are more options for deployment as well as additionalmanagement cluster capabilities that can be leveraged. Examplesdisclosed herein facilitate making workload domain configuration andmanagement easier than prior techniques.

A management cluster is a group of physical machines and virtualmachines (VM) that host core cloud infrastructure components necessaryfor managing a software defined data center (SDDC) in a cloud computingenvironment that supports customer services. Cloud computing allowsubiquitous, convenient, on-demand network access to a shared pool ofconfigurable computing resources. A cloud computing customer can requestallocations of such resources to support services required by thosecustomers. For example, when a customer requests to run one or moreservices in the cloud computing environment, one or more workloaddomains may be created based on resources in the shared pool ofconfigurable computing resources.

Virtual networks can be used with virtual machines in SDDC and/or othercloud or cloud-like computing environments. Virtual networks can bemanaged (e.g., using NSX sold by VMware, Inc.) using policies and rules.Network and other infrastructure is configured for consumption byapplications. Virtual network(s) are provisioned for such applicationsto be deployed in the SDDC.

Certain examples provide multi-cloud management systems that manage acombination of public and private clouds (e.g., a hybrid cloudenvironment) running a variety of computing processes from traditionalprocesses to virtual machines to container (e.g., cloud native)workloads. Automation and pre-defined policies providing high levels ofagility and flexibility for developers and lines of business whilemaintaining governance and control.

An example multi-cloud management system can provision infrastructureand application resources with a choice of consumption (e.g.,application programming interface (API), Catalog, command line interface(CLI), etc.) based on pre-defined policies and permissions. Provisioningand maintenance of resources are automated through creation ofblueprints (e.g., models) that include components of requested servicesalong with their relationships, including a mix of VM andcontainer-based services. Integration can be extended to third partyand/or customer applications, tools, etc.

In a virtual infrastructure, such as a multi-cloud management system, anendpoint is a provisioned resource completing a provisioning processsuch as a public cloud resource (e.g., a web service such as Amazon WebServices (AWS), etc.), a virtual appliance (e.g., an externalorchestrator appliance, etc.), a private cloud (e.g., hosted by VMwarevSphere™, Microsoft Hyper-V™, etc.), etc. For example, a service has anendpoint that provides a specific function or feature of that service.The service may have multiple endpoints. For example, a catalog serviceprovides catalog features via an endpoint for a shell/user interfaceapplication service to consume. Endpoints can include physicalendpoints, virtual endpoints, Internet Protocol Address Management(IPAM) endpoints, etc. An endpoint type defines a set of one or moremethods/functions that can be invoked, and an endpoint or endpointinstance is the object that implements or provides access to themethods/functions. An endpoint adapter enables the endpoint and themanagement system to communicate with each other. The endpoint adaptercan facilitate/enable data/instruction communication, security, accesscontrol, redundancy, auditing, etc. If properly registered, aninfrastructure-driven workflow can be launched for the endpoint via theendpoint adapter, for example.

However, in multi-cloud management systems, it is hard or evenimpossible to extend a virtual platform and/or other solution to managea new kind of endpoint adapter that is not originally defined as part ofthe platform. For example, by default, the virtual platform has supportto manage only the three major public clouds: AWS, Microsoft Azure, andGoogle Compute Platform (GCP). Traditionally, to extend the virtualplatform with new kind of endpoint requires changing the platform codebase (e.g., to support the new endpoint type) and restarting the virtualplatform.

Example Virtualization Environments

Many different types of virtualization environments exist. Three exampletypes of virtualization environment are: full virtualization,paravirtualization, and operating system virtualization.

Full virtualization, as used herein, is a virtualization environment inwhich hardware resources are managed by a hypervisor (e.g., a virtualmachine monitor or computer software, hardware and/or firmware thatcreates and runs virtual machines) to provide virtual hardware resourcesto a virtual machine. In a full virtualization environment, the virtualmachines do not have direct access to the underlying hardware resources.In a typical full virtualization environment, a host operating systemwith embedded hypervisor (e.g., VMware ESXi®) is installed on the serverhardware. Virtual machines including virtual hardware resources are thendeployed on the hypervisor. A guest operating system is installed in thevirtual machine. The hypervisor manages the association between thehardware resources of the server hardware and the virtual resourcesallocated to the virtual machines (e.g., associating physical randomaccess memory (RAM) with virtual RAM). Typically, in fullvirtualization, the virtual machine and the guest operating system haveno visibility and/or direct access to the hardware resources of theunderlying server. Additionally, in full virtualization, a full guestoperating system is typically installed in the virtual machine while ahost operating system is installed on the server hardware. Example fullvirtualization environments include VMware ESX®, Microsoft Hyper-V®, andKernel Based Virtual Machine (KVM).

Paravirtualization, as used herein, is a virtualization environment inwhich hardware resources are managed by a hypervisor to provide virtualhardware resources to a virtual machine and guest operating systems arealso allowed direct access to some or all of the underlying hardwareresources of the server (e.g., without accessing an intermediate virtualhardware resource). In a typical paravirtualization system, a hostoperating system (e.g., a Linux-based operating system) is installed onthe server hardware. A hypervisor (e.g., the Xen® hypervisor) executeson the host operating system. Virtual machines including virtualhardware resources are then deployed on the hypervisor. The hypervisormanages the association between the hardware resources of the serverhardware and the virtual resources allocated to the virtual machines(e.g., associating physical random access memory (RAM) with virtualRAM). In paravirtualization, the guest operating system installed in thevirtual machine is configured also to have direct access to some or allof the hardware resources of the server. For example, the guestoperating system may be precompiled with special drivers that allow theguest operating system to access the hardware resources without passingthrough a virtual hardware layer. For example, a guest operating systemmay be precompiled with drivers that allow the guest operating system toaccess a sound card installed in the server hardware. Directly accessingthe hardware (e.g., without accessing the virtual hardware resources ofthe virtual machine) may be more efficient, may allow for performance ofoperations that are not supported by the virtual machine and/or thehypervisor, etc.

Operating system virtualization is also referred to herein as containervirtualization. As used herein, operating system virtualization refersto a system in which processes are isolated in an operating system. In atypical operating system virtualization system, a host operating systemis installed on the server hardware. Alternatively, the host operatingsystem may be installed in a virtual machine of a full virtualizationenvironment or a paravirtualization environment. The host operatingsystem of an operating system virtualization system is configured (e.g.,utilizing a customized kernel) to provide isolation and resourcemanagement for processes that execute within the host operating system(e.g., applications that execute on the host operating system). Theisolation of the processes is known as a container. Several containersmay share a host operating system. Thus, a process executing within acontainer is isolated the process from other processes executing on thehost operating system. Thus, operating system virtualization providesisolation and resource management capabilities without the resourceoverhead utilized by a full virtualization environment or aparavirtualization environment. Alternatively, the host operating systemmay be installed in a virtual machine of a full virtualizationenvironment or a paravirtualization environment. Example operatingsystem virtualization environments include Linux Containers LXC and LXD,Docker™, OpenVZ™, etc.

In some instances, a data center (or pool of linked data centers) mayinclude multiple different virtualization environments. For example, adata center may include hardware resources that are managed by a fullvirtualization environment, a paravirtualization environment, and anoperating system virtualization environment. In such a data center, aworkload may be deployed to any of the virtualization environments.

Example Provisioning and Subscription Systems and Methods

Certain examples enable client definition and deployment ofarchitecturally complex virtual computing environments. Such virtualcomputing environments can include multiple machines, software, etc.While some systems (e.g., vRealize Automation®, etc.) providefunctionality to enable common scenarios “out of the box”, certainexamples enable customization for specific functionality. Certainexamples provide a flexible and powerful extensibility mechanism thatenables cloud administrators and/or other users, for example, to finetune a resource provisioning process by blocking, pausing, and/orotherwise (temporarily) halting the provisioning process to enableexecution of custom scripts and/or functionality before provisioningcontinues. In certain examples, the provisioning process can fail if aspecified criterion is not met.

In certain examples, an event broker service (EBS) providespublish-subscribe functionality to allow other services to subscribe tomessages regarding system process events (e.g., provisioning, etc.) andreceive updates regarding process execution. For example, the EBS usesREST (Representational State Transfer) APIs (Application ProgrammingInterface) and/or other client-server communication protocol forpublish-subscribe communication. The event broker REST API providesfeatures for managing subscriptions, event topics, events, and messages,for example.

In certain examples, the EBS allows services to register and manageevent topics, publish events, and manage subscriptions by eventconsumers. Event consumers can register/subscribe to retrieve and/orotherwise receive events according to event topic, etc. Event producers(e.g., services, service providers, etc.) publish events to the EBS,and, after receiving an event, the EBS notifies event consumers that aresubscribed to the event.

A blueprint is a specification for a service (e.g., a virtual computingservice, etc.). A blueprint specifies components of a service, such asinput parameters, submission and read-only forms, sequence of actions,provisioning, etc. Service blueprints can be created to provision customresources that have previously been created according to certainparameters, for example. The blueprint stores the parameters inassociation with the resource to enable the resource to be instantiatedagain. A blueprint, such as a service blueprint, can be published as acatalog item for selection via a catalog of available services forprovisioning, for example. When a catalog item is selected, thecorresponding resource is provisioned according to the parametersspecified in the blueprint, for example.

Certain examples provide a composition blueprint service (CBP) thatenables customers (e.g., via a designer) to define their complexmulti-machine systems including dependencies between components andsoftware to install on each component. An event broker service (EBS)works with the CBP and provides publish-subscribe functionality forprovisioning and/or other system process, in which blocking subscribersare able to process events first, before non-blocking subscribers. Byintegrating CBP and EBS, clients can extend, modify, and/or otherwisealter flow of a provisioning process. The CBP can construct a dependencytree for virtual computing system components and provision thecomponents in order (or in parallel if no dependency exists betweencomponents) as each component transitions among a plurality of lifecyclestates including allocation, provisioning, software installation,deallocation, continuing operations, etc. For each lifecycle state, asubscription topic can be defined in the EBS, which enables customersand/or other services to subscribe and listen for events related to thesubscribed topic.

In certain examples, when the CBP initializes (e.g., is selected viacatalog, started by a service, instantiated in a VM, etc.), the CBPsubscribes (e.g., listens, monitors, etc.) to subscription topicscorresponding to lifecycle states as a non-blocking subscriber. As anon-blocking subscriber, client processes can accommodate events withpriority over the CBP as a non-blocking subscriber, for example.

During provisioning of resource(s) corresponding to a selectedblueprint, the CBP sends an event to EBS at each lifecycle stage. Apayload of the event includes relevant information about currentoperation, deployment parameters, status, etc.

FIG. 1 depicts an example system 100 constructed in accordance with theteachings of this disclosure for managing a cloud computing platform.The example system 100 includes an application director 106 and a cloudmanager 138 to manage a cloud computing platform provider 110 asdescribed in more detail below. As described herein, the example system100 facilitates management of the cloud provider 110 and does notinclude the cloud provider 110. Alternatively, the system 100 could beincluded in the cloud provider 110.

The cloud computing platform provider 110 provisions virtual computingresources (e.g., virtual machines, or “VMs,” 114) that may be accessedby users of the cloud computing platform 110 (e.g., users associatedwith an administrator 116 and/or a developer 118) and/or other programs,software, device, etc.

An example application 102 of FIG. 1 includes multiple VMs 114. Theexample VMs 114 of FIG. 1 provide different functions within theapplication 102 (e.g., services, portions of the application 102, etc.).One or more of the VMs 114 of the illustrated example are customized byan administrator 116 and/or a developer 118 of the application 102relative to a stock or out-of-the-box (e.g., commonly availablepurchased copy) version of the services and/or application components.Additionally, the services executing on the example VMs 114 may havedependencies on other ones of the VMs 114.

As illustrated in FIG. 1, the example cloud computing platform provider110 may provide multiple deployment environments 112, for example, fordevelopment, testing, staging, and/or production of applications. Theadministrator 116, the developer 118, other programs, and/or otherdevices may access services from the cloud computing platform provider110, for example, via REST (Representational State Transfer) APIs(Application Programming Interface) and/or via any other client-servercommunication protocol. Example implementations of a REST API for cloudcomputing services include a vCloud Administrator Center™ (vCAC) and/orvRealize Automation™ (vRA) API and a vCloud Director™ API available fromVMware, Inc. The example cloud computing platform provider 110provisions virtual computing resources (e.g., the VMs 114) to providethe deployment environments 112 in which the administrator 116 and/orthe developer 118 can deploy multi-tier application(s). One particularexample implementation of a deployment environment that may be used toimplement the deployment environments 112 of FIG. 1 is vCloud DataCentercloud computing services available from VMware, Inc.

In some examples disclosed herein, a lighter-weight virtualization isemployed by using containers in place of the VMs 114 in the developmentenvironment 112. Example containers 114 a are software constructs thatrun on top of a host operating system without the need for a hypervisoror a separate guest operating system. Unlike virtual machines, thecontainers 114 a do not instantiate their own operating systems. Likevirtual machines, the containers 114 a are logically separate from oneanother. Numerous containers can run on a single computer, processorsystem and/or in the same development environment 112. Also like virtualmachines, the containers 114 a can execute instances of applications orprograms (e.g., an example application 102 a) separate fromapplication/program instances executed by the other containers in thesame development environment 112.

The example application director 106 of FIG. 1, which may be running inone or more VMs, orchestrates deployment of multi-tier applications ontoone of the example deployment environments 112. As illustrated in FIG.1, the example application director 106 includes a topology generator120, a deployment plan generator 122, and a deployment director 124.

The example topology generator 120 generates a basic blueprint 126 thatspecifies a logical topology of an application to be deployed. Theexample basic blueprint 126 generally captures the structure of anapplication as a collection of application components executing onvirtual computing resources. For example, the basic blueprint 126generated by the example topology generator 120 for an online storeapplication may specify a web application (e.g., in the form of a Javaweb application archive or “WAR” file including dynamic web pages,static web pages, Java servlets, Java classes, and/or other property,configuration and/or resources files that make up a Java webapplication) executing on an application server (e.g., Apache Tomcatapplication server) that uses a database (e.g., MongoDB) as a datastore. As used herein, the term “application” generally refers to alogical deployment unit, including one or more application packages andtheir dependent middleware and/or operating systems. Applications may bedistributed across multiple VMs. Thus, in the example described above,the term “application” refers to the entire online store application,including application server and database components, rather than justthe web application itself. In some instances, the application mayinclude the underlying hardware and/or virtual computing hardwareutilized to implement the components.

The example basic blueprint 126 of FIG. 1 may be assembled from items(e.g., templates) from a catalog 130, which is a listing of availablevirtual computing resources (e.g., VMs, networking, storage, etc.) thatmay be provisioned from the cloud computing platform provider 110 andavailable application components (e.g., software services, scripts, codecomponents, application-specific packages) that may be installed on theprovisioned virtual computing resources. The example catalog 130 may bepre-populated and/or customized by an administrator 116 (e.g., IT(Information Technology) or system administrator) that enters inspecifications, configurations, properties, and/or other details aboutitems in the catalog 130. Based on the application, the exampleblueprints 126 may define one or more dependencies between applicationcomponents to indicate an installation order of the applicationcomponents during deployment. For example, since a load balancer usuallycannot be configured until a web application is up and running, thedeveloper 118 may specify a dependency from an Apache service to anapplication code package.

The example deployment plan generator 122 of the example applicationdirector 106 of FIG. 1 generates a deployment plan 128 based on thebasic blueprint 126 that includes deployment settings for the basicblueprint 126 (e.g., virtual computing resources' cluster size, CPU,memory, networks, etc.) and an execution plan of tasks having aspecified order in which virtual computing resources are provisioned andapplication components are installed, configured, and started. Theexample deployment plan 128 of FIG. 1 provides an IT administrator witha process-oriented view of the basic blueprint 126 that indicatesdiscrete actions to be performed to deploy the application. Differentdeployment plans 128 may be generated from a single basic blueprint 126to test prototypes (e.g., new application versions), to scale up and/orscale down deployments, and/or to deploy the application to differentdeployment environments 112 (e.g., testing, staging, production). Thedeployment plan 128 is separated and distributed as local deploymentplans having a series of tasks to be executed by the VMs 114 provisionedfrom the deployment environment 112. Each VM 114 coordinates executionof each task with a centralized deployment module (e.g., the deploymentdirector 124) to ensure that tasks are executed in an order thatcomplies with dependencies specified in the application blueprint 126.

The example deployment director 124 of FIG. 1 executes the deploymentplan 128 by communicating with the cloud computing platform provider 110via a cloud interface 132 to provision and configure the VMs 114 in thedeployment environment 112. The example cloud interface 132 of FIG. 1provides a communication abstraction layer by which the applicationdirector 106 may communicate with a heterogeneous mixture of cloudprovider 110 and deployment environments 112. The deployment director124 provides each VM 114 with a series of tasks specific to thereceiving VM 114 (herein referred to as a “local deployment plan”).Tasks are executed by the VMs 114 to install, configure, and/or startone or more application components. For example, a task may be a scriptthat, when executed by a VM 114, causes the VM 114 to retrieve andinstall particular software packages from a central package repository134. The example deployment director 124 coordinates with the VMs 114 toexecute the tasks in an order that observes installation dependenciesbetween VMs 114 according to the deployment plan 128. After theapplication has been deployed, the application director 106 may beutilized to monitor and/or modify (e.g., scale) the deployment.

The example cloud manager 138 of FIG. 1 interacts with the components ofthe system 100 (e.g., the application director 106 and the cloudprovider 110) to facilitate the management of the resources of the cloudprovider 110. The example cloud manager 138 includes a blueprint manager140 to facilitate the creation and management of multi-machineblueprints and a resource manager 144 to reclaim unused cloud resources.The cloud manager 138 may additionally include other components formanaging a cloud environment.

The example blueprint manager 140 of the illustrated example manages thecreation of multi-machine blueprints that define the attributes ofmultiple virtual machines as a single group that can be provisioned,deployed, managed, etc. as a single unit. For example, a multi-machineblueprint may include definitions for multiple basic blueprints thatmake up a service (e.g., an e-commerce provider that includes webservers, application servers, and database servers). A basic blueprintis a definition of policies (e.g., hardware policies, security policies,network policies, etc.) for a single machine (e.g., a single virtualmachine such as a web server virtual machine and/or container).Accordingly, the blueprint manager 140 facilitates more efficientmanagement of multiple virtual machines and/or containers than manuallymanaging (e.g., deploying) basic blueprints individually. Examplemanagement of multi-machine blueprints is described in further detail inconjunction with FIG. 2.

The example blueprint manager 140 of FIG. 1 additionally annotates basicblueprints and/or multi-machine blueprints to control how workflowsassociated with the basic blueprints and/or multi-machine blueprints areexecuted. As used herein, a workflow is a series of actions anddecisions to be executed in a virtual computing platform. The examplesystem 100 includes first and second distributed execution manager(s)(DEM(s)) 146A and 146B to execute workflows. According to theillustrated example, the first DEM 146A includes a first set ofcharacteristics and is physically located at a first location 148A. Thesecond DEM 146B includes a second set of characteristics and isphysically located at a second location 148B. The location andcharacteristics of a DEM may make that DEM more suitable for performingcertain workflows. For example, a DEM may include hardware particularlysuited for performance of certain tasks (e.g., high-end calculations),may be located in a desired area (e.g., for compliance with local lawsthat require certain operations to be physically performed within acountry's boundaries), may specify a location or distance to other DEMSfor selecting a nearby DEM (e.g., for reducing data transmissionlatency), etc. Thus, the example blueprint manager 140 annotates basicblueprints and/or multi-machine blueprints with capabilities that can beperformed by a DEM that is labeled with the same or similarcapabilities.

The resource manager 144 of the illustrated example facilitates recoveryof cloud computing resources of the cloud provider 110 that are nolonger being activity utilized. Automated reclamation may includeidentification, verification and/or reclamation of unused,underutilized, etc. resources to improve the efficiency of the runningcloud infrastructure.

FIG. 2 illustrates an example implementation of the blueprint 126 as amulti-machine blueprint generated by the example blueprint manager 140of FIG. 1. In the illustrated example of FIG. 2, three example basicblueprints (a web server blueprint 202, an application server blueprint204, and a database (DB) server blueprint 206) have been created (e.g.,by the topology generator 120). For example, the web server blueprint202, the application server blueprint 204, and the database serverblueprint 206 may define the components of an e-commerce online store.

The example blueprint manager 140 provides a user interface for a userof the blueprint manager 140 (e.g., the administrator 116, the developer118, etc.) to specify blueprints (e.g., basic blueprints and/ormulti-machine blueprints) to be assigned to an instance of amulti-machine blueprint 208. For example, the user interface may includea list of previously generated basic blueprints (e.g., the web serverblueprint 202, the application server blueprint 204, the database serverblueprint 206, etc.) to allow selection of desired blueprints. Theblueprint manager 140 combines the selected blueprints into thedefinition of the multi-machine blueprint 208 and stores informationabout the blueprints in a multi-machine blueprint record defining themulti-machine blueprint 208. The blueprint manager 140 may additionallyinclude a user interface to specify other characteristics correspondingto the multi-machine blueprint 208. For example, a creator of themulti-machine blueprint 208 may specify a minimum number and a maximumnumber of each blueprint component of the multi-machine blueprint 208that may be provisioned during provisioning of the multi-machineblueprint 208.

Accordingly, any number of virtual machines (e.g., the virtual machinesassociated with the blueprints in the multi-machine blueprint 208)and/or containers may be managed collectively. For example, the multiplevirtual machines corresponding to the multi-machine blueprint 208 may beprovisioned based on an instruction to provision the multi-machineblueprint 208, may be power cycled by an instruction, may be shut downby an instruction, may be booted by an instruction, etc. As illustratedin FIG. 2, an instruction to provision the multi-machine blueprint 208may result in the provisioning of a multi-machine service 210 formedfrom one or more VMs 114 that includes virtualized web server(s) 210A,virtualized application server(s) 210B, and virtualized databaseserver(s) 210C. The number of virtual machines and/or containersprovisioned for each blueprint may be specified during the provisioningof the multi-machine blueprint 208 (e.g., subject to the limitsspecified during creation or management of the multi-machine blueprint208).

The multi-machine blueprint 208 maintains the reference to the basicblueprints 202, 204, 206. Accordingly, changes made to the blueprints(e.g., by a manager of the blueprints different than the manager of themulti-machine blueprint 208) may be incorporated into futureprovisioning of the multi-machine blueprint 208. Accordingly, anadministrator maintaining the source blueprints (e.g., an administratorcharged with managing the web server blueprint 202) may change or updatethe source blueprint and the changes may be automatically propagated tothe machines provisioned from the multi-machine blueprint 208. Forexample, if an operating system update is applied to a disk imagereferenced by the web server blueprint 202 (e.g., a disk image embodyingthe primary disk of the web server blueprint 202), the updated diskimage is utilized when deploying the multi-machine blueprint.Additionally, the blueprints may specify that the machines 210A, 210B,210C of the multi-machine service 210 provisioned from the multi-machineblueprint 208 operate in different environments. For example, somecomponents may be physical machines, some may be on-premises virtualmachines, and some may be virtual machines at a cloud service.

Several multi-machine blueprints 208 may be generated to provide one ormore varied or customized services. For example, if virtual machinesdeployed in the various States of the United States require differentsettings, a multi-machine blueprint 208 could be generated for eachstate. The multi-machine blueprints could reference the same buildprofile and/or disk image, but may include different settings specificto each state. For example, the deployment workflow may include anoperation to set a locality setting of an operating system to identify aparticular state in which a resource is physically located. Thus, asingle disk image may be utilized for multiple multi-machine blueprints208 reducing the amount of storage space for storing disk imagescompared with storing a disk image for each customized setting.

FIG. 3 illustrates an example installation of deployed appliances orvirtual appliances (vAs) (e.g., VMs 114 and/or containers 114 a) andassociated virtualized servers acting as hosts for deployment ofcomponent servers (e.g., Web server, application server, databaseserver, etc.) for a customer. The vAs can be deployed as an automationtool, for example, used to deliver VMs and associated applications foron-premises automation and/or handling of external cloud resources(e.g., Microsoft Azure™, Amazon Web Services™, etc.).

As shown in the example of FIG. 3, an installation 300 includes a loadbalancer (LB) 310 to assign tasks and/or manage access among a pluralityof vAs 320, 322, 324. Each vA 320-324 is a deployed VM 114 and/orcontainer 114 a. In this example, the vA 320 communicates with aplurality of component or host servers 330, 332, 334, 336 which storecomponents for execution by users (e.g., Web server 210A with Webcomponents, App server 210B with application components, DB server 210Cwith database components, etc.). As shown in the example of FIG. 3,component servers 334, 336 can stem from component server 330 ratherthan (or in addition to) directly from the virtual appliance 320,although the vA 320 can still communicate with such servers 334, 336.The LB 310 enables the multiple vAs 320-324 and multiple servers 330-336to appear as one device to a user. Access to functionality can then bedistributed among appliances 320-324 by the LB 310 and among servers330-336 by the respective appliance 320, for example. The LB 310 can useleast response time, round-robin, and/or other method to balance trafficto vAs 320-324 and servers 330-336, for example.

In the example installation 300, each vA 320, 322, 324 includes amanagement endpoint 340, 342, 344. Each component server 330, 332, 334,336 includes a management agent 350, 352, 354, 356. The managementagents 350-356 can communicate with their respective endpoint 340 tofacilitate transfer of data, execution of tasks, etc., for example.

In certain examples, the management agents 350-356 synchronize componentservers 330-336 with the vA 320-234 and facilitate host access andassociated services (e.g., hostd, ntpd, sfcbd, slpd, wsman, vobd, etc.).The management agents 350-356 can communicate with their respectiveendpoint 340 to facilitate transfer of data, execution of tasks, etc.,for example. The relationship between management endpoint 340, 342, 344and associated management agents 350, 352, 354, 356 can be used todeploy and install software on multiple component machines 330, 332,334, 336.

In certain examples, a graphical user interface associated with a frontend of the load balancer 310 guides a customer through one or morequestions to determine system requirements for the installation 300.Once the customer has completed the questionnaire and provided firewallaccess to install the agents 350-356, the agents 350-356 communicatewith the endpoint 340 without customer involvement. Thus, for example,if a new employee needs a Microsoft Windows® machine, a manager selectsan option (e.g., clicks a button, etc.) via the graphical user interfaceto install a VM 114 and/or container 114 a that is managed through theinstallation 300. To the user, he or she is working on a single machine,but behind the scenes, the virtual appliance (vA) 320 is accessingdifferent servers 330-336 depending upon what functionality is to beexecuted.

In certain examples, agents 350-356 are deployed in a same data centeras the endpoint 340 to which the agents 350-356 are associated. Thedeployment can include a plurality of agent servers 330-336 distributedworldwide, and the deployment can be scalable to accommodate additionalserver(s) with agent(s) to increase throughput and concurrency, forexample.

FIG. 4 illustrates an example implementation of the vA 320. In theexample of FIG. 4, the vA 320 includes an example service provisioner410, an example orchestrator 420, an example event broker 430, anexample authentication provider 440, an example internal reverse proxy450, an example data storage 460, an example catalog 465, an examplerepository 467, an example subscription manager 470, and exampleservices 480. The components 410, 420, 430, 440, 450, 460, 470, 480 ofthe vA 320 can be implemented by one or more of the VMs 114 and/orcontainers 114 a, for example. The example service provisioner 410provides services to provision interfaces (e.g., Web interface,application interface, etc.) for the vA 320. The example orchestrator(e.g., vCO) 420 is an embedded or internal orchestrator that canleverage a provisioning manager, such as the application director 106and/or cloud manager 138, to provision services but is embedded in thevA 320. For example, the orchestrator 420 can be used to invoke ablueprint to provision a manager for services. In some examples, theorchestrator 420 includes a library of workflows that can be selectedfor execution.

Example services 480 can include catalog services, identity services,component registry services, approval services, resource managementservices, event broker services, IaaS, XaaS (“Anything-as-a-Service”),etc. Catalog services provide a user interface via which a user canrequest provisioning of different preset environments (e.g., a VM 114including an operating system and software and some customization,etc.), for example. Identity services facilitate authentication andauthorization of users and assigned roles, for example. The componentregistry maintains information corresponding to installed and deployedservices (e.g., uniform resource locators for services installed in aVM/vA, etc.), for example. The approval services provide a method bywhich a request to provision a virtual machine (or service) can beapproved by a system administrator(s). The resource management servicescan control the leasing, expiration and reclamation of managedresources. The event broker 430 provides a messaging broker forevent-based communication, for example. The IaaS provisions one or moreVMs and/or containers for a customer via the vA 320. The XaaS can extendthe provisioning to also request, approve, provision, operate, anddecommission any type of catalog items (e.g., storage, applications,accounts, and anything else that the catalog provides as a service).

The example event broker 430 provides a mechanism to handle tasks whichare transferred between the services 190 and the orchestrator 420. Theexample authentication provider 440 (e.g., VMware Horizon™ services,etc.) authenticates access to services and data, for example.

The components of the vA 320 access each other through REST API callsbehind the internal reverse proxy 450 (e.g., a high availability (HA)proxy HAProxy) which provides a high availability load balancer andproxy for Transmission Control Protocol (TCP)- and Hypertext TransferProtocol (HTTP)-based application requests. In this example, the proxy450 forwards communication traffic from within the vA 320 and/or betweenvAs 320, 322, 324 of FIG. 3 to the appropriate component(s) of the vA320. In certain examples, services access the local host/proxy 450 on aparticular port, and the call is masked by the proxy 450 and forwardedto the particular component of the vA 320. Since the call is masked bythe proxy 450, components can be adjusted within the vA 320 withoutimpacting outside users.

In the example vA 320 of FIG. 4, the example services 480, the exampleevent broker 430, the example subscription manager 470, and the exampleorchestrator 420 implement an example workflow subscription service toenable services and/or other clients to subscribe to provisioningworkflow events. Using the subscription service, provisioning workflowscan be extended to include additional tasks. The example workflowsubscription service implemented by the vA 320 enables a customer, suchas the tenant administrator 116, or any other authorized user, service,machine, etc., to control when provisioning workflows (or workflowrelated to provisioning activities) are performed based on eventsreported by service(s) 480 to the event broker 430. In some examples,the workflow subscription service further allows the tenantadministrator 116 and/or other client to control when workflows areperformed based on events coupled with user-specified and/or otherprocess-specified conditions.

As used herein, an event topic describes a set of events having a samelogical intent and a same structure. Each event is an instance of anevent topic. Further an event topic is a type of event message that issent to the event broker 430 by one or more of the services 480. Anevent can indicate a change in the state of one of the services 480 thatproduces the event (or any of the entities managed by any such one ofthe services 480), for example. An event is an informational element (ordata structure) in which information about an event occurrence isrecorded. An event notification or message transports information aboutthe event between the various services 480 and the event broker 430 andbetween the event broker 430 and the subscription manager 470.

In some examples, event topics include a post approval event topic, apre-approval event topic, an event log default event topic, a blueprintconfiguration event topic, a resource reclamation event topic, abusiness group configuration event topic, an orchestration serverconfiguration event topic, a machine lifecycle event topic, a machineprovisioning event topic, etc. The post approval and pre-approval eventtopics are associated with the approval service and can be used totrigger workflows associated with obtaining enterprise approvals for anoperation. (For example, if a user would like to provision a new virtualmachine, the pre-approval event topic may be used to generate a workflowthat will require a set of administrative approvals be obtained beforethe virtual machine is provisioned.) The event log default event topicrepresents the addition of an entry in an event log and can be generatedby an event log service. The event log can be a recordation of any of aset of occurrences/operations performed by any of the components of thevA 320. The blueprint configuration event topic can be associated withthe creation, deletion or updating of a blueprint configuration and canbe generated by a composition service. The resource reclamationcompletion event can represent a resource lease expiring and reclamationof the resource subject to the expired lease. The resource reclamationcompletion event can be generated by a resource management service. Thebusiness group configuration event topic can represent a business groupbeing created, updated or deleted and can be generated by an identityservice. The orchestration server configuration (XaaS) event topic canrepresent an orchestrator server configuration being created, updated,deleted or modified and can be generated by an advanced-designerservice. The machine lifecycle event topic can represent an IaaS actionbeing run on a provisioned machine and can be generated by an IaaSservice. The machine provisioning event topic can represent an IaaSmachine in the process of being provisioned and can be generated by anIaaS service.

Each event topic has an associated event schema. In some examples, whencreating a workflow script to be executed in connection with asubscription, the workflow script can be configured to include inputparameters (or a single input parameter) that use/consume all (or some)of the data included in the data fields of the event payload/schema. Thename and type of such input parameters are defined to match the name andtype specified in the event schema, for example. In some such examples,the subscription manager 470 extracts the event schema from the eventmessage and supplies the extracted event schema as input parameters tothe orchestrator 420 for use in executing the custom workflow script. Inaddition, the workflow script can be configured to generate outputparameters that match a desired schema. Thus, the generated outputparameters that result from executing the custom workflow script aresupplied by the orchestrator 420 to the subscription manager 470 afterthe workflow script is executed and the subscription manager 470includes the output parameters in a reply message transmitted back tothe event broker 430 for subsequent usage by other workflowsubscriptions and/or for use by the service that produced the event thattriggered the workflow. In addition to input parameters, thesubscription manager 470 supplies a workflow identifier and any otherinformation needed by the orchestrator 420 to execute the workflowscript.

For event topic subscribers, an event notification/message includes anevent payload that identifies the event topic associated with the eventnotification (e.g. the event of interest) and includes event schemainformation. In some examples, upon receiving the event schemainformation, the subscription manager 470 processes the event schemainformation to identify an event of interest. Workflow informationassociated with the event is also sent to the orchestrator 420, whichuses an associated workflow identifier (and, if appropriate, inputparameters) to execute the workflow 420. In some examples, the workflowidentifier indicates that a specialized workflow is to be executed. Thespecialized workflow can be a workflow containing tasks and/or stepsembodied in and/or corresponding to an executable script that the tenantadministrator entered at the tenant administrator work station 116 (seeFIG. 1), for example. When this occurs, a storage address of the datastorage 460 at which the script is stored can be transmitted to theworkflow orchestrator 420. In some such examples, the workfloworchestrator 420 responds by executing the tasks/steps contained at thestorage address of the data storage 460. In some examples, uponcompletion of the workflow, the workflow orchestrator 420 can notify thesubscription manager 470. The subscription manager 470 can respond tothe notification by notifying the event broker 430. In some examples,the notification transmitted to the event broker 430 can includeinformation about any aspect of the subscription and/or about executionof the workflow, etc.

By way of example, Table 1 illustrates an example provisioning eventtopic schema. In this example, the provisioning event topic schema isrelated to the provisioning of a virtual machine. In the illustratedexample, the machine is identified using an identifier, “id,” a machinename, a machine identifier on the hypervisor, a machine owner, and amachine type. As illustrated, the machine can be a physical machine or avirtual machine and includes a set of properties. The machine propertiescan include a blueprint name, a component identifier, a component typeidentifier, an endpoint identifier, a request identifier and a lifecyclestate that indicates a state, phase and event. In addition, the eventschema includes a virtual machine event field, a workflow next statefield, a virtual machine add or update properties field and a virtualmachine delete properties field.

TABLE 1 Example Provisioning Event Topic Schema { machine : { id :STRING,  /* IaaS machine ID */ name : STRING,  /* machine name */externalReference : STRING,  /* machine ID on the hypervisor */ owner :STRING,  /* machine owner */ type : INTEGER,  /* machine type: 0 -virtual machine; 1 - physical machine; 2 - cloud machine */ properties :Properties  /* machine properties, see notes below how to expose virtualmachine properties */ }, blueprintName : STRING, /* blueprint name */componentId : STRING, /* component id */ componentTypeId : STRING, /*component type id */ endpointId : STRING, /* endpoint id */ requestId :STRING, /* request id */ lifecycleState : {  /* see Life Cycle StateDefinitions*/ state : STRING, phase : STRING, event : STRING },virtualMachineEvent : STRING, /* fire an event on that machine - onlyprocessed by Manager Service as consumer */ workflowNextState : STRING,/* force the workflow to a specific state - only processed by ManagerService as consumer */ virtualMachineAddOrUpdateProperties :Properties, /* properties on the machine to add/update - only processedby Manager Service as consumer */ virtualMachineDeleteProperties :Properties /* properties to remove from the machine - only processed byManager Service as consumer */ }

Based on the foregoing description, the example workflow subscriptionservice implemented by the example vA 320 provides features that permitworkflows to be triggered/executed based on a combination of events anduser-selected/user-specified/machine-generated conditions. The workflowsubscription system disclosed herein enables the triggering ofadditional workflow/workflow tasks by making selections (e.g., via agraphical user interface, program instructions, etc.). Further, thetriggering of the workflow can be made contingent upon any number ofconditions.

FIG. 5 illustrates an example implementation of the vA 320 to process anexample blueprint 126 and manage associated subscription(s) according tosubscription type, etc. As shown in the example of FIG. 5, a requester502 requests the blueprint 126 from the catalog 465. The blueprint 126can include a complex multi-machine service blueprint 208, for example,to define a complex multi-machine system 210 including a plurality ofcomponents 210A-210C and software and dependencies between componentsand software, for example. A complex blueprint service (CBP) 504 workswith the catalog 465 and the orchestrator 420 to provision the blueprint126, 208. The orchestrator 420 implements a composition 506 to provisiona service 480 according to the blueprint 126, 208. For example, an IaaS508 can be a service 480 provisioned by the composition 506 according tothe blueprint 126, 208.

In certain examples, provisioning via the blueprint 126, 208 can occurvia a container and/or other VM. In certain examples, a host environmentspawns a container for code execution via an endpoint. For example, anapplication programming interface (API) call, such as a REST API call,etc., a user interface input, a stimulus, and/or trigger can launchexecution of code in the container in the host environment. Code can beexecuted in an isolated, enclosed, detached, or “sandboxed” fashionusing a container, for example. Thus, code snippets, scripts, etc., suchas Java code, PowerShell™ script, Python code, etc., can be executed viathe isolated environment of the container without affecting the rest ofthe virtual environment.

In certain examples, the repository 467 stores information to supportinfrastructure deployed using the virtual appliance 320. For example,endpoint information can be stored in the repository 467 (and/or therepository 134 of the example of FIG. 1).

Example Cloud Management and Endpoint Adapter Registration,Provisioning, and Operation

In certain examples, the virtual appliance 320 and/or anotherimplementation of the VM 114 is used to instantiate a multi-cloudcompute management platform. To enable partners to extend themulti-cloud compute management platform to facilitate management ofendpoints (e.g., cloud, hypervisor, etc.), a central repository 134and/or 467 is provided for endpoint adapters (e.g., AliCloud™,VirtuStream™, SoftLAYER™, etc.). The repository 134 and/or 467 specifiesthe endpoint adapter and provides for a REST-based, API/contract forcommunication between the registered adapter and the platform.

In certain examples, the cloud provider 110 implements a plurality ofVMs 114 and/or containers 114 a in a deployed environment 112. Eachendpoint adapter is run as a separated process in a container 114 a, VM114, physical machine, etc. The endpoint adapter is registered to aprovisioning service endpoint adapter registry including metadata suchas a uniform resource locator (URL) and/or other indicator of a locationat which REST and/or other endpoints are enumerated (e.g., computes,networks, storages, etc.), provisioned resource, resource operations,monitoring, etc.

Once an endpoint adapter is registered to the system (e.g., added to theendpoint adapter registry), the endpoint adapter becomes a “first classcitizen” giving the endpoint adapter native rights to multi-cloudmanagement platform access. Thus, for the platform, which providescompute, allocation, and/or other services, there is no differencebetween internal endpoint adapters and third party external endpointadapters once the endpoint adapters are added to the endpoint registry.Using the endpoint registry, partners can deploy and manage resourcesfrom a hypervisor and/or cloud system. For example, cloud providers canbe supported via the endpoint registry to deploy applications as a setof VMs with proper software installed on them. Additionally, while oneVM 114 and/or container 114 a supports the cloud management platform,other VMs 114 and/or containers 114 a can support endpoints andinteraction between the cloud management platform and external content,for example. Thus, if an external endpoint is corrupted and/or otherwisebecomes unsupported, its VM 114/container 114 a can be deactivatedwithout impacting the VM 114/container 114 a running the cloudmanagement platform, for example.

In certain examples, a third party endpoint adapter must be incorporatedinto the cloud management platform. Previously, this was impossiblewithout rewriting the code base and manually updating the API. However,certain examples enable a third party endpoint adapter to be added tothe endpoint registry so that the platform can define a protocol andassociated API for endpoints on the registry. The platform then does notdistinguish between embedded endpoint adapters and added endpointadapters that are on the endpoint registry. In certain examples, aregistry entry for an endpoint includes metadata for the endpointadapter and instructions for how the endpoint is called, etc. Theendpoint adapter can execute in the same or different VM 114 and/orcontainer 114 a (e.g., virtual appliance 320, etc.) as the cloudmanagement platform and/or other endpoints, for example. For example,the endpoint adapter can run in a separate process and register to theendpoint registry.

In certain examples, when an endpoint managed by a third partycontributor adapter is to be added to the platform, a cloud managementsystem host communicates with the external endpoint adapter to identifythe endpoint adapter and add the endpoint adapter to the endpointregistry. The host can leverage an interface and the registry tocommunicate with the endpoint to install a new endpoint, register theendpoint, and remove the endpoint without impact to the rest of thehosted cloud system via the endpoint registry, for example.

For example, FIG. 6A illustrates an example VM 114 (e.g., a virtualappliance 320, etc.) configured as a cloud management platform 600. Theexample cloud management platform 600 includes a platform host 602, aplatform interface 604, and a component registry 606 to identifyinternal endpoint(s) 608, external endpoint(s) 610, and/or othercomponent(s) such as custom interface(s) 612, etc. The example componentregistry 606 includes an identification of one or more componentadapter(s) 614. A user device 616 can interact with the cloud managementplatform 600 via the interface 604 to register and/or access anendpoint, interface, and/or other component using the component registry606, for example.

Using the example platform 600, one or more external devices 616 candeploy and manage resources from clouds and/or hypervisors that alreadyhave accounts with the platform 600. Applications can be deployed as aset of VMs with applicable software installed on them. For example,cloud providers can deploy applications as a set of VMs configured andinstalled with software via the multi-cloud management platform 600.Using the component registry 606, a component adapter 614 can be definedand incorporated into the platform 600 to be trusted and made availablefor execution (e.g., by the user device 616 and/or other process, etc.).The component registry 606 includes an indication of the componentadapter 614, associated protocol and API(s), etc. External endpoints610, internal endpoints 608, custom interfaces 612, and/or othercomponents are treated the same by the platform 600 once included in theregistry 606. In the registry 606, metadata is registered with respectto the component adapter 614 and in conjunction with aninstruction/format/protocol regarding how to call and/or otherwiseexecute the component adapter 614 to interact with the component 608,610, 612 for example. The component adapter 614 can run in the same ordifferent VM 114 and/or container 114 a as the cloud management platform600, for example. For example, the endpoint adapter can execute in aseparate process and register to the component registry 606.

In the example of FIG. 6B, rather than directly interfacing with thecloud management system or platform 600, the custom interface 612 isassociated with the external endpoint 610 surfaced by the platform 600.Thus, the host 602 can control what external endpoint 610 is incommunication with the platform 600, and a configuration for theendpoint's adapter 614 can be stored in the component registry 606. Thecustom interface 612, provided by a third party, for example, can accessthe platform 600 as allowed by the external endpoint's configuration.

FIG. 7 illustrates an example system 700 configuration in which theplatform 600 is implemented in one container 114 a while the externalendpoint 610 and the custom interface 612 are running in othercontainers 114 a in communication with the container 114 a running thecloud platform 600. In the example system 700 of FIG. 7,applications/services can leverage the endpoint 610, interface 612,etc., via the platform 600, but one or more of the components 610, 612can easily be disconnected from the cloud platform 600 should suchaction be warranted (e.g., the endpoint container becomes too greedy forresources, is vulnerable to attack, etc.). Thus, when an endpoint 610container 114 a fails, it fails itself and does not impact the rest ofthe system 600, 700. Thus, partner(s) can register endpoint(s) 610,interface(s) 612, and/or other component(s) with the platform 600 toextend the platform 600 and provide load balancing and scalability incontainer(s) 114 a and/or other VM(s) 114 apart from the platform 600.As shown in the example of FIG. 7, the platform 600, external endpoint610, and custom interface 612 can be on different networks and stillcommunicate via the platform 600.

Thus, partners can extend the multi-cloud managementsoftware-as-a-service (SaaS) platform 600 by directly or indirectlyregistering components, such as endpoints 610, interfaces 612, etc., toextend capabilities of the platform 600 to include capabilities servedby an external device or system (e.g., running on a different process,host, etc.) while subject to control and security constraint of theplatform 600 and its host 602. The example registry 606 maintainsmetadata associated with systems to serve the custom interface 612 andprovide data to the interface 612 based on user input in a givencontext. The registry 606 metadata can include a system identifier, anaccess mechanism (e.g., a uniform resource indicator (URI), credentials,authentication mechanism, certificate, etc.), and additional informationabout the interface 612 (e.g., internal URLs) and backend services tofeed the interface 612, for example.

Upon request of the custom interface 612, the multi-cloud managementsystem 600 retrieves the associated metadata from the registry 606,using the host 602 as a reverse proxy, and the partner system can beconnected using the specified authentication mechanism to retrieve theinterface 612 (e.g., including HTML, CSS, scripts, images, fonts, etc.)and serve the interface 612 to a requestor. When the custom interface612 requests data from the backend system, the request goes to themulti-cloud management platform 600 and its host 602 via the platforminterface 604 to recognize the interface 612, perform a security checkof the interface 612 and its request, and, through reverse proxy basedon a user context in the request, connect to the backend to fetch dataand serve the data back through the requesting interface 612, forexample. In certain examples, to fetch data, a structure describes therequest, and the structure specifies: a user context, an action, abackend (e.g., URL, URI, etc.) to be consumed, etc. For securityreasons, only those requests that correspond to the required structureare forwarded to the (partner) backend system.

FIGS. 8-9 depict example data flow diagrams 800, 900 to register a newendpoint in the cloud management system 600. FIG. 8 shows an exampledata flow 800 to initiate registration by the cloud platform host 602with the external endpoint 610, custom interface 612, etc. At 802, thecloud platform host 602 starts a registration service to communicatewith the external endpoint 610, the custom interface 612, etc. Theinitiation of the service triggers the external endpoint 610, custominterface 612, etc., and/or to register 804 with the component registry606. Thus, the host 602 starts all services, including dynamic services.When an external (e.g., non-embedded) service is started, the serviceregisters metadata from the endpoint 610 and/or custom interface 612 tothe component registry service 606. The component registry or componentregistry service 606 is a stateful service that maintains informationabout all registered endpoints 608, 610, interfaces 612, etc.

In certain examples, an instance of an external component such as anendpoint 610, custom interface 612, etc., can be created via theregistration service 802 triggered by the host 602. The servicevalidates data provided against a schema for the component and retrievesthe component (e.g., an IaaS repository endpoint, user interface, etc.)from the component registry 606. The custom interface 612 and/or otherendpoint 610 can be updated based on new configuration, data, etc., andthe service 802 can be called to save the updated component data withthe registry 606. A provider of the data (e.g., the platform host 602,user device 616, etc.) can then receive an indication of endpoint updatesuccess, for example.

In certain examples, the user device 616 seeks to manage (e.g.,enumerate/discover, provision/destroy, power on/off, etc.) resourcessuch as VMs, containers, etc., on a given endpoint 608, 610 such as ahypervisor, a public cloud, a physical endpoint, etc. Alternatively orin addition, the device 616 seeks to serve a custom interface 612leveraging the cloud management platform 600 and its host 602. FIG. 9shows an example data flow 900 for the user device 616 to register a newcustom interface 612 and/or other external endpoint 610 and itscomponent adapter 614 with the component registry 606.

At 902, the user device 616 selects a component type (e.g., userinterface, hypervisor, cloud, physical endpoint, etc.) via the interface604. At 904, the interface 604 retrieves an interface form correspondingto the component type from the host 602. At 906, the host 602 requests acomponent registration interface from the endpoint adapter 614. Thecomponent adapter 614 provides the registration interface to theplatform interface 604 via the host 602, and, at 908, the interface 604provides the registration interface to the user device 616.

At 910, a loop is triggered to gather data and generate an interface toregister the component 610, 612 via the component adapter 614. At 912,data is provided from the user device 616 to the interface 604, whichupdates the interface form 914 and provides the form to the componentadapter 614. The component adapter 614 responds to the added data bygenerating an updated interface 916 and sending the updated interfaceback to the platform interface 604. The platform interface 604 providesthe updated registration interface 918 to the user device 616, whichcontinues in the loop 910 to enter data until all data for the componentregistration has been entered.

At 920, the user device 616 submits the completed data set to theinterface 604, which, in turn, submits the data 922 to the host 602. Thehost 602 provides the data 924 to the component adapter 614, whichaccepts and processes the data and generates a registration status 926(e.g., successful registration, registration failure, more informationneeded, approval needed, etc.) for the host 602. At 928, the host 602provides the registration status to the interface 604, which provides930 feedback to the user device 616.

Thus, in certain examples, when an interface 612 and/or other endpoint610 managed by a third party contributor adapter is to be added and/ormodified, the user device 616 connects to the interface 604, and theinterface 604 is in communication with the host 602, which is incommunication with the component adapter 614. The host 602, via thecomponent adapter 614, provides metadata from available endpointadapter(s) 614 in the registry 606 so that the user device 616 candetermine which adapter to use. If the selected component adapter 614 isa third party external endpoint or interface adapter 614, data isprovided by the user device 616 to establish communication with thecomponent adapter 614 through the multi-cloud management system host 602(e.g., reverse proxy). Data is sent by the component adapter 614 to theplatform interface 604 and made available to the user device 616. Theuser device 616 can submit data to register a cloud account, forexample, and the partner component adapter 614 can provide additionalmetadata such as project, region(s), etc. The user device 616 can selecta project to manage, and the selection is submitted to the platforminterface 604, which provides the selection via reverse proxy to thehost 602, which interprets the user data and communicates with thecomponent adapter 614. The component adapter 614 responds with feedbackto let the host 602 and the user device 616 know how the submittedrequest has been processed by the endpoint 610 and/or interface 612, forexample.

In certain examples, cloud accounts can be registered as administratorendpoints 610 and stored in the component registry 606. Other thirdparty adapters can be stored in the component registry 606 as well. Thecustom interface 612 can be a graphical user interface, data interface,etc., whose metadata is stored in the registry 606 to provide access tocontent, network resources, etc., via the cloud or multi-cloud, forexample.

In certain examples, the interface 604 can be implemented and providedin a plurality of ways. For example, the interface 604 can beimplemented as a data-driven interface in which the external endpoint610 registers an endpoint registration schema (e.g., URL, useridentification, password, tenant, etc.). Such a data-driven interfacecan be technology-agnostic so that third parties do not have to be boundto a particular concrete interface technology, and the interface 604 caninstead evolve to new technology, library, paradigm, etc. However, acomplex schema (model) is used to describe complex interfaces includingdependencies, steps, and/or phases to enter connection/credentialdetails, etc.

In other examples, the interface 604 can be implemented as a contentinterface such that the platform host 602 asks the component adapter 614(on a certain endpoint 610 with endpoint registration metadata, etc.) toprovide the interface form (e.g. HTML, JavaScript, etc.). Such ascontent-driven interface can include an ability to provide very complexinterfaces via the component adapter 614. The interface 604 is definedin a particular framework, technology, paradigm, and/or library, forexample. The interface provided by the component adapter 614 uses aconcrete framework to describe a desired state, for example.

For example, in an OpenStack (VIO) case, the endpoint registration formasks the user device 616 for a URL, user and password, and then queriesthe backend (e.g., host 602 and endpoint adapter 614) for projects ortenants and allows the user device 616 to select a project for which toregister the current endpoint 610.

In certain examples, a photon model component registry 606 is part of aphoton model that provides a unified model for systems and applicationmanagement across multiple infrastructures for which photon adaptershave been written. Photon model APIs can be used to deploy and managesystems, from applications to infrastructure, in a single coherent modeland implementation. The photon model can enumerate and synchronize bothphoton APIs and customer native APIs (e.g. from on-premise and/or cloudproviders) and associated state resources, for example. Thus, the photonmodel enables application management as a service across public andprivate clouds.

An example photon-model-adapter endpoint registry model can berepresented as follows:

AdapterEndpointConfig

-   -   id*: String (the endpoint identifier/type e.g. openstack,        virtustream, softlayer, etc.)    -   name*: String (endpoint name that can be human readable, 110 n,        il8 n, etc.)    -   customProperties: Map<String,String> for various props (this is        derived from ResourceState)        -   icon provided by convention as an entry in the map with key            ‘icon’ and value, and a path to the icon resource (e.g.,            resources/openstack/static-content/openstack.png)    -   adapterEndpoints: Map<String,String> which keeps mapping an        endpoint/service type to a service/factory link        -   key: String (the endpoint type, e.g.            ENDPOINT_CONFIG_ADAPTER, ENDPOINT_CONFIG_ADAPTER UI,            PROVISIONING_ADAPTER, INSTANCE_ADAPTER, ENUMERATION_ADAPTER,            POWER_ADAPTER, etc.)        -   link: String (the Service's SELF_LINK)            The photon model adapter registry is part of the photon            model and is used to help minimize the requirements            (dependencies) towards third party adapter implementations            (e.g., to depend on photon-model and xenon only), for            example.

While an example manner of implementing an endpoint registry in a cloudcomputing environment is illustrated in FIGS. 1-9, one or more of theelements, processes and/or devices illustrated in FIGS. 1-9 may becombined, divided, re-arranged, omitted, eliminated and/or implementedin any other way. Further, the example application director 106, examplecloud provider 110, example cloud manager 138, example distributedexecution managers 146A, 146B, example multi-machine service 210,example load balancer 310, example virtual appliances 320-324, examplecomponent servers 330-336, example management endpoints 340-344, examplemanagement agents 350-356, example service provisioner 410, exampleorchestrator 420, example event broker 430, example authenticationprovider 440, example internal reverse proxy 450, example data storage460, example catalog 465, example repository 467, example subscriptionmanager 470, example services 480, example requestor 502, examplecomposition blueprint service 504, example composition 506, example IaaS508, example subscriber 510, example cloud management platform 600,example host 602, example interface 604, example component registry 606,example internal endpoint 608, example external endpoint 610, examplecustom interface 612, example component adapter 614, example user device616, and/or, more generally, the example system 100, 300, 600 of FIGS.1-9 can be implemented by hardware, software, firmware and/or anycombination of hardware, software and/or firmware. Thus, for example,any of the example application director 106, example cloud provider 110,example cloud manager 138, example distributed execution managers 146A,146B, example multi-machine service 210, example load balancer 310,example virtual appliances 320-324, example component servers 330-336,example management endpoints 340-344, example management agents 350-356,example service provisioner 410, example orchestrator 420, example eventbroker 430, example authentication provider 440, example internalreverse proxy 450, example data storage 460, example catalog 465,example repository 467, example subscription manager 470, exampleservices 480, example requestor 502, example composition blueprintservice 504, example composition 506, example IaaS 508, examplesubscriber 510, example cloud management platform 600, example host 602,example interface 604, example component registry 606, example internalendpoint 608, example external endpoint 610, example custom interface612, example component adapter 614, example user device 616, and/or,more generally, the example system 100, 300, 600 of FIGS. 1-9 can beimplemented by one or more analog or digital circuit(s), logic circuits,programmable processor(s), application specific integrated circuit(s)(ASIC(s)), programmable logic device(s) (PLD(s)) and/or fieldprogrammable logic device(s) (FPLD(s)). When reading any of theapparatus or system claims of this patent to cover a purely softwareand/or firmware implementation, at least one of the example applicationdirector 106, example cloud provider 110, example cloud manager 138,example distributed execution managers 146A, 146B, example multi-machineservice 210, example load balancer 310, example virtual appliances320-324, example component servers 330-336, example management endpoints340-344, example management agents 350-356, example service provisioner410, example orchestrator 420, example event broker 430, exampleauthentication provider 440, example internal reverse proxy 450, exampledata storage 460, example catalog 465, example repository 467, examplesubscription manager 470, example services 480, example requestor 502,example composition blueprint service 504, example composition 506,example IaaS 508, example subscriber 510, example cloud managementplatform 600, example host 602, example interface 604, example componentregistry 606, example internal endpoint 608, example external endpoint610, example custom interface 612, example component adapter 614,example user device 616, and/or, more generally, the example system 100,300, 600 of FIGS. 1-9 is/are hereby expressly defined to include atangible computer readable storage device or storage disk such as amemory, a digital versatile disk (DVD), a compact disk (CD), a Blu-raydisk, etc. storing the software and/or firmware. Further still, theexample application director 106, example cloud provider 110, examplecloud manager 138, example distributed execution managers 146A, 146B,example multi-machine service 210, example load balancer 310, examplevirtual appliances 320-324, example component servers 330-336, examplemanagement endpoints 340-344, example management agents 350-356, exampleservice provisioner 410, example orchestrator 420, example event broker430, example authentication provider 440, example internal reverse proxy450, example data storage 460, example catalog 465, example repository467, example subscription manager 470, example services 480, examplerequestor 502, example composition blueprint service 504, examplecomposition 506, example IaaS 508, example subscriber 510, example cloudmanagement platform 600, example host 602, example interface 604,example component registry 606, example internal endpoint 608, exampleexternal endpoint 610, example custom interface 612, example componentadapter 614, example user device 616, and/or, more generally, theexample system 100, 300, 600 of FIGS. 1-9 may include one or moreelements, processes and/or devices in addition to, or instead of, thoseillustrated in FIGS. 1-9, and/or may include more than one of any or allof the illustrated elements, processes and devices.

Flowcharts representative of example machine readable instructions thatmay be executed to implement the example application director 106,example cloud provider 110, example cloud manager 138, exampledistributed execution managers 146A, 146B, example multi-machine service210, example load balancer 310, example virtual appliances 320-324,example component servers 330-336, example management endpoints 340-344,example management agents 350-356, example service provisioner 410,example orchestrator 420, example event broker 430, exampleauthentication provider 440, example internal reverse proxy 450, exampledata storage 460, example catalog 465, example repository 467, examplesubscription manager 470, example services 480, example requestor 502,example composition blueprint service 504, example composition 506,example IaaS 508, example subscriber 510, example cloud managementplatform 600, example host 602, example interface 604, example componentregistry 606, example internal endpoint 608, example external endpoint610, example custom interface 612, example component adapter 614,example user device 616, and/or, more generally, the example system 100,300, 600 of FIGS. 1-9 are shown in FIGS. 10-14. In these examples, themachine readable instructions implement programs for execution by aprocessor such as the processor 1512, 1612, 1714, and/or 1812 shown inthe example processor platform 1500-1800 discussed below in connectionwith FIGS. 15-18. The programs may be embodied in software stored on atangible computer readable storage medium such as a CD-ROM, a floppydisk, a hard drive, a digital versatile disk (DVD), a Blu-ray disk, or amemory associated with the processor 1512-1812, but the entire programand/or parts thereof could alternatively be executed by a device otherthan the processor 1512-1812 and/or embodied in firmware or dedicatedhardware. Further, although the example programs are described withreference to the flowcharts illustrated in FIGS. 10-14, many othermethods of deploying, evaluating, and installing services on componentservers in accordance with the teachings of this disclosure mayalternatively be used. For example, the order of execution of the blocksmay be changed, and/or some of the blocks described may be changed,eliminated, or combined.

As mentioned above, the example processes of FIGS. 10-14 may beimplemented using coded instructions (e.g., computer and/or machinereadable instructions) stored on a tangible computer readable storagemedium such as a hard disk drive, a flash memory, a read-only memory(ROM), a compact disk (CD), a digital versatile disk (DVD), a cache, arandom-access memory (RAM) and/or any other storage device or storagedisk in which information is stored for any duration (e.g., for extendedtime periods, permanently, for brief instances, for temporarilybuffering, and/or for caching of the information). As used herein, theterm tangible computer readable storage medium is expressly defined toinclude any type of computer readable storage device and/or storage diskand to exclude propagating signals and to exclude transmission media. Asused herein, “tangible computer readable storage medium” and “tangiblemachine readable storage medium” are used interchangeably. In someexamples, the example processes of FIGS. 10-14 may be implemented usingcoded instructions (e.g., computer and/or machine readable instructions)stored on a non-transitory computer and/or machine readable medium suchas a hard disk drive, a flash memory, a read-only memory, a compactdisk, a digital versatile disk, a cache, a random-access memory and/orany other storage device or storage disk in which information is storedfor any duration (e.g., for extended time periods, permanently, forbrief instances, for temporarily buffering, and/or for caching of theinformation). As used herein, the term non-transitory computer readablemedium is expressly defined to include any type of computer readablestorage device and/or storage disk and to exclude propagating signalsand to exclude transmission media. As used herein, when the phrase “atleast” is used as the transition term in a preamble of a claim, it isopen-ended in the same manner as the term “comprising” is open ended.Comprising and all other variants of “comprise” are expressly defined tobe open-ended terms. Including and all other variants of “include” arealso defined to be open-ended terms. In contrast, the term consistingand/or other forms of consist are defined to be close-ended terms.

FIG. 10 depicts a flowchart representative of computer readableinstructions that may be executed to implement endpoint registration inthe virtual cloud management system 600, 700. An example program 1000 isillustrated in FIG. 10. At block 1002, an endpoint adapter configurationis registered. For example, the user device 616 interacts with the host602 via the interface 604 to provide information to register aninterface 612 and/or other endpoint 610 and the associated componentadapter 614 with the component registry 606. Once registered, thecomponent adapters 614 can be made available for access to instances ofthe interface 612 and/or other endpoint 610 via the registry 606.

At block 1004, a list or set of available component adapterconfigurations is provided. For example, the registry 606 can provide alist or set of available endpoint adapter configurations to the platformhost 602, which can surface them via the interface 604.

At block 1006, if known, a component adapter configuration is retrieved(block 1008) based on an identifier. For example, the user device 616can query the list/set of component adapters 614 made available via theinterface 604 based on an identifier associated with a particularendpoint 610, interface 612, or associated adapter 614. At block 1010,if the identifier is unknown, then the list or set of component adapterconfigurations can be queried by a criterion such as endpoint type. Forexample, the user device 616 can query the list/set of componentadapters 614 made available via the interface 604 based on a desiredtype of endpoint (e.g., hypervisor, private cloud, SaaS, IaaS, etc.). Atblock 1012, the component adapter configuration result is provided tothe user device 616. For example, based on the query from the userdevice 616, the interface 604 provides a selection to the host 602,which queries the component registry 606 for the desired componentadapter configuration. The result is then passed back to the host 602,which provides the configuration to the user device 616 via theinterface 604, for example.

FIG. 11 provides further detail regarding an implementation ofregistering a component adapter 614 configuration (block 1002) of theexample flow diagram of FIG. 10. At block 1102, the user device 616connects to a backend system (e.g., the multi-cloud management platform600). At block 1104, the backend system provides metadata identifyingadapters 614 in the registry 606. At block 1106, an adapter 614 isselected by the user device 616 from the registry 606. At block 1108,the user device 616 provides data to register the custom interface 612and/or other endpoint 610 and its adapter configuration using theadapter 614 definition in the component registry 606.

At block 1110, the adapter configuration is registered with the backendsystem. For example, the configuration is noted as metadata inconnection with the component adapter 614 in the registry 606. At block1112, a result of the registration is provided. For example, feedbackregarding a result of the registration is provided to the user device616 via the host 602 and interface 604. The component adapter 614 isthen available for use to connect to the endpoint 610, display theinterface 612, etc.

In certain examples, a registered endpoint 608, 610 is consumed withincertain constraints to extend the multi-cloud platform 600 to provideadditional interface(s) 612, etc. such extension and associatedinteraction can be facilitated according to a defined schema havingspecific restrictions. For example, if a VM 114 is to be restarted, theschema specifies how and when to restart the VM 114. If a snapshot is tobe created, the schema can specify data to be specified such as name,available snapshot(s), default snapshot to which to revert based on acertain condition/criterion, etc.

For example, such as shown in FIG. 6B, the custom interface 612 accessesthe endpoint 610 exposed by the cloud management platform 600 with apayload including header data specifying who is the user, what theoperation wants to do (e.g., action), etc. For the action, a securitycheck can be performed by the host 602 to determine whether the user hasrights to perform the action/operation, and data can be combined withrequirements to validate. After validation, the interface 612 (and thehost 602) knows how to communicate with a corresponding partner adapter614 (e.g., the request is saved and endpoint/endpoint type is known,etc.) and can look up endpoint 610 location and associated protocol touse to communicate with the endpoint adapter 614. The interface 612 canthen communicate with the partner adapter 614.

Thus, for example, the interface 612 can make a synchronous call via abrowser to request and wait for a response from the cloud managementsystem 600 (via the host 602 and the interface 604). The host 602performs a verification and security check and identifies, using theregistry 606, which partner adapter 614 is being requested. The host 602determines a location of the desired adapter 614 and a protocol/schemafor communication with the adapter 614 from the registry 606. The host602 contacts the adapter 614 and provides a payload from the interface612 (e.g., from a user via a browser, etc.), and the adapter 614provides feedback to the host 602, which performs an additional securitycheck to make sure the information can be routed to that tenant (e.g.,the interface 612, etc.). If acceptable, the host 602 provides theinformation to the requesting tenant interface 612 (e.g., return theinformation to the user in the browser, etc.).

In certain examples, an electronic contract is formed between themanagement platform 600 and one or more partner devices/systems 616. Thecontract enables partner devices 616 to contribute certain interfacessuch as to register an endpoint, show a resource, conduct resourceoperations, etc. Additionally, the partner device 616 can contribute thecustom interface 612, etc. Since the interface 612 is now served by apartner adapter 614, the host 602 is not concerned with certificateswhen serving the interface 612 and can provide the interface 612 in anapplication technology or framework, which can be different from thetechnology/framework used to build the interface 612. Rather thanexposing a web server to the cloud, which can lead to cross-sidescripting issues and insecure communications, certain examples enable acustom interface 612 to be provided via the platform host 602 (and theendpoint 608, 610). The host 602 connects to the adapter 614 andfacilitates a smooth, secure authentication verification and serving ofcontent for use, display, etc.

FIG. 12 illustrates a flow diagram of a method 1200 to serve a custominterface 612 as a resource with the cloud management platform 600(e.g., extending the cloud management platform 600 based on thefunctionality of the interface 612, etc.). At block 1202, an endpoint isregistered. For example, a cloud administrator wants to register a newendpoint 610 of unsupported type. As discussed above with respect toFIG. 10, the new endpoint 610 can be registered an added to the registry606, for example. At block 1204, data is fetched for the new registeredendpoint 610 to serve the custom interface 612. For example, data toform the interface 612 and enable its functionality can be retrievedfrom a backend system via a partner adapter 614, which can enable theconnection with a partner system and/or process to provide data to drivethe custom interface 612, for example. At block 1206, the custominterface 612 is available for use by one or more users, devices 616,processes, etc.

FIG. 13 provides further detail regarding an implementation ofregistering an endpoint 610 (block 1202) of the example flow diagram ofFIG. 12. At block 1302, the cloud administrator and/or the user device616 requests addition of an external endpoint (e.g., an AliCloudendpoint, etc.) to the cloud management platform 600. For example, theuser device 616 communicates with the interface 604 to notify the host602 of the endpoint request.

At block 1304, the host 602 processes the request and identifies abackend system and/or process to register the endpoint 610. For example,the host 602 identifies the custom interface 612 associated with theendpoint 610 and, based on an endpoint type and/or other identifyinginformation, determines a URI for a backend partner system to contact toresolve the endpoint 610 registration. At block 1306, the host 602serves as a reverse proxy to retrieve content from the partner systemand mask interaction with the partner system from the custom interface612 and/or associated user device 616.

At block 1308, the host 602 forwards the endpoint request to the partnersystem and/or process. At block 1310, the partner system and/or processresponds to the host 602. For example, the partner system provides thecustomer interface 612 to the host 602 in response to the request. Atblock 1312, the host 602, via the interface 604, provides avisualization of the custom interface 612 to the user device 616, cloudadministrator, etc.

FIG. 14 provides further detail regarding an implementation of fetchingdata for the registered endpoint 610 (block 1204) of the example flowdiagram of FIG. 12. At block 1402, the custom interface 612 requestsdata for the endpoint 610 from the multi-cloud management platform 600.At block 1404, the host 602 identifies the request for data and performsa security check for integrity, authentication, and authorization of thecustom interface 612 and data request. At block 1406, results of thesecurity check are analyzed.

If the security check is a success, then, at block 1408, the host 602contacts the backend system/process via a URI found in the adapterregistry 606 with the host 602 as the reverse proxy. At block 1410, thehost 602 forwards the data request from the custom interface 612 to thepartner system/process. At block 1412, the backend partnersystem/process responds with requested data. At block 1414, the host 602provides the fetched data to the custom interface 612 (e.g., directlyand/or via the endpoint 610, user device 616, etc.). Thus, the custominterface 612 can be displayed and enabled with functionality based onthe fetched data, for example.

However, if the security check is unsuccessful, then, at block 1416,feedback is provided to the custom interface 612 rather than fetcheddata. Thus, if the custom interface 612 is not authenticated and/or isnot authorized to interact with the partner system and/or process, anotification is provided as feedback to the interface 612 (e.g.,directly and/or via the endpoint 610, user device 616, etc.).

FIG. 15 is a block diagram of an example processor platform 1500structured to execute the instructions of FIGS. 10-14 to implement theexample systems, operation, and management of FIGS. 1-9. The processorplatform 1500 of the illustrated example includes a processor 1512. Theprocessor 1512 of the illustrated example is hardware. For example, theprocessor 1512 can be implemented by one or more integrated circuits,logic circuits, microprocessors or controllers from any desired familyor manufacturer.

The processor 1512 of the illustrated example includes a local memory1513 (e.g., a cache), and executes instructions to implement the examplecloud management platform or system 600 or portions thereof, such as theexample host 602, interface 604, registry 606, and/or internal endpoint608. The processor 1512 of the illustrated example is in communicationwith a main memory including a volatile memory 1514 and a non-volatilememory 1516 via a bus 1518. The volatile memory 1514 may be implementedby Synchronous Dynamic Random Access Memory (SDRAM), Dynamic RandomAccess Memory (DRAM), RAMBUS Dynamic Random Access Memory (RDRAM) and/orany other type of random access memory device. The non-volatile memory1516 may be implemented by flash memory and/or any other desired type ofmemory device. Access to the main memory 1514, 1516 is controlled by amemory controller.

The processor platform 1500 of the illustrated example also includes aninterface circuit 1520. The interface circuit 1520 may be implemented byany type of interface standard, such as an Ethernet interface, auniversal serial bus (USB), and/or a PCI express interface.

In the illustrated example, one or more input devices 1522 are connectedto the interface circuit 1520. The input device(s) 1522 permit(s) a userto enter data and commands into the processor 1512. The input device(s)can be implemented by, for example, an audio sensor, a microphone, akeyboard, a button, a mouse, a touchscreen, a track-pad, a trackball,isopoint and/or a voice recognition system. In some examples, the inputdevice(s) 1522 are used to implement the tenant administrator workstation 116 (see FIG. 1).

One or more output devices 1524 are also connected to the interfacecircuit 1520 of the illustrated example. The output devices 1524 can beimplemented, for example, by display devices (e.g., a light emittingdiode (LED), an organic light emitting diode (OLED), a liquid crystaldisplay, a cathode ray tube display (CRT), a touchscreen, a tactileoutput device, a printer and/or speakers). The interface circuit 1520 ofthe illustrated example, thus, typically includes a graphics drivercard, a graphics driver chip or a graphics driver processor. In someexamples, the output device(s) 1524 are used to implement the tenantadministrator work station 116 (see FIG. 1).

The interface circuit 1520 of the illustrated example also includes acommunication device such as a transmitter, a receiver, a transceiver, amodem and/or network interface card to facilitate exchange of data withexternal machines (e.g., computing devices of any kind) via a network1526 (e.g., an Ethernet connection, a digital subscriber line (DSL), atelephone line, coaxial cable, a cellular telephone system, etc.).

The processor platform 1500 of the illustrated example also includes oneor more mass storage devices 1528 for storing software and/or data.Examples of such mass storage devices 1528 include flash devices, floppydisk drives, hard drive disks, optical compact disk (CD) drives, opticalBlu-ray disk drives, RAID systems, and optical digital versatile disk(DVD) drives.

Coded instructions 1532 representative of the example machine readableinstructions of FIGS. 10-14 may be stored in the mass storage device1528, in the volatile memory 1514, in the non-volatile memory 1516,and/or on a removable tangible computer readable storage medium such asa CD or DVD.

In the example of FIG. 15, the processor 1512 implements the examplecloud management platform or system 600 including the example host 602,interface 604, registry 606, and/or internal endpoint 608, etc. Incertain examples, as discussed herein, the hardware of processor 1512 isvirtualized using virtualization such as VMs and/or containers.

FIG. 16 is a block diagram of an example processor platform 1700structured to execute the instructions of FIGS. 10-14 to implement theexample systems, operation, and management of FIGS. 1-9. The processorplatform 1600 of the illustrated example includes a processor 1612. Theprocessor 1612 of the illustrated example is hardware. For example, theprocessor 1612 can be implemented by one or more integrated circuits,logic circuits, microprocessors or controllers from any desired familyor manufacturer.

The processor 1612 of the illustrated example includes a local memory1613 (e.g., a cache), and executes instructions to implement the examplecloud management platform or system 600 or portions thereof, such as theexample external endpoint 610. The processor 1612 of the illustratedexample is in communication with a main memory including a volatilememory 1614 and a non-volatile memory 1616 via a bus 1618. The volatilememory 1614 may be implemented by Synchronous Dynamic Random AccessMemory (SDRAM), Dynamic Random Access Memory (DRAM), RAMBUS DynamicRandom Access Memory (RDRAM) and/or any other type of random accessmemory device. The non-volatile memory 1616 may be implemented by flashmemory and/or any other desired type of memory device. Access to themain memory 1614, 1616 is controlled by a memory controller.

The processor platform 1600 of the illustrated example also includes aninterface circuit 1620. The interface circuit 1620 may be implemented byany type of interface standard, such as an Ethernet interface, auniversal serial bus (USB), and/or a PCI express interface.

In the illustrated example, one or more input devices 1622 are connectedto the interface circuit 1620. The input device(s) 1622 permit(s) a userto enter data and commands into the processor 1612. The input device(s)can be implemented by, for example, an audio sensor, a microphone, akeyboard, a button, a mouse, a touchscreen, a track-pad, a trackball,isopoint and/or a voice recognition system. In some examples, the inputdevice(s) 1622 are used to implement the tenant administrator workstation 116 (see FIG. 1).

One or more output devices 1624 are also connected to the interfacecircuit 1620 of the illustrated example. The output devices 1624 can beimplemented, for example, by display devices (e.g., a light emittingdiode (LED), an organic light emitting diode (OLED), a liquid crystaldisplay, a cathode ray tube display (CRT), a touchscreen, a tactileoutput device, a printer and/or speakers). The interface circuit 1620 ofthe illustrated example, thus, typically includes a graphics drivercard, a graphics driver chip or a graphics driver processor. In someexamples, the output device(s) 1624 are used to implement the tenantadministrator work station 116 (see FIG. 1).

The interface circuit 1620 of the illustrated example also includes acommunication device such as a transmitter, a receiver, a transceiver, amodem and/or network interface card to facilitate exchange of data withexternal machines (e.g., computing devices of any kind) via a network1626 (e.g., an Ethernet connection, a digital subscriber line (DSL), atelephone line, coaxial cable, a cellular telephone system, etc.).

The processor platform 1600 of the illustrated example also includes oneor more mass storage devices 1628 for storing software and/or data.Examples of such mass storage devices 1628 include flash devices, floppydisk drives, hard drive disks, optical compact disk (CD) drives, opticalBlu-ray disk drives, RAID systems, and optical digital versatile disk(DVD) drives.

Coded instructions 1632 representative of the example machine readableinstructions of FIGS. 10-14 may be stored in the mass storage device1628, in the volatile memory 1614, in the non-volatile memory 1616,and/or on a removable tangible computer readable storage medium such asa CD or DVD.

In the example of FIG. 16, the processor 1612 implements the exampleexternal endpoint 610, etc. In certain examples, as discussed herein,the hardware of processor 1612 is virtualized using virtualization suchas VMs and/or containers.

FIG. 17 is a block diagram of an example processor platform 1700structured to execute the instructions of FIGS. 10-14 to implement theexample systems, operation, and management of FIGS. 1-9. The processorplatform 1700 of the illustrated example includes a processor 1712. Theprocessor 1712 of the illustrated example is hardware. For example, theprocessor 1712 can be implemented by one or more integrated circuits,logic circuits, microprocessors or controllers from any desired familyor manufacturer.

The processor 1712 of the illustrated example includes a local memory1713 (e.g., a cache), and executes instructions to implement the examplecloud management platform or system 600 or portions thereof, such as theexample custom interface 612. The processor 1712 of the illustratedexample is in communication with a main memory including a volatilememory 1714 and a non-volatile memory 1716 via a bus 1718. The volatilememory 1714 may be implemented by Synchronous Dynamic Random AccessMemory (SDRAM), Dynamic Random Access Memory (DRAM), RAMBUS DynamicRandom Access Memory (RDRAM) and/or any other type of random accessmemory device. The non-volatile memory 1716 may be implemented by flashmemory and/or any other desired type of memory device. Access to themain memory 1714, 1716 is controlled by a memory controller.

The processor platform 1700 of the illustrated example also includes aninterface circuit 1720. The interface circuit 1720 may be implemented byany type of interface standard, such as an Ethernet interface, auniversal serial bus (USB), and/or a PCI express interface.

In the illustrated example, one or more input devices 1722 are connectedto the interface circuit 1720. The input device(s) 1722 permit(s) a userto enter data and commands into the processor 1712. The input device(s)can be implemented by, for example, an audio sensor, a microphone, akeyboard, a button, a mouse, a touchscreen, a track-pad, a trackball,isopoint and/or a voice recognition system. In some examples, the inputdevice(s) 1722 are used to implement the tenant administrator workstation 116 (see FIG. 1).

One or more output devices 1724 are also connected to the interfacecircuit 1720 of the illustrated example. The output devices 1724 can beimplemented, for example, by display devices (e.g., a light emittingdiode (LED), an organic light emitting diode (OLED), a liquid crystaldisplay, a cathode ray tube display (CRT), a touchscreen, a tactileoutput device, a printer and/or speakers). The interface circuit 1720 ofthe illustrated example, thus, typically includes a graphics drivercard, a graphics driver chip or a graphics driver processor. In someexamples, the output device(s) 1724 are used to implement the tenantadministrator work station 116 (see FIG. 1).

The interface circuit 1720 of the illustrated example also includes acommunication device such as a transmitter, a receiver, a transceiver, amodem and/or network interface card to facilitate exchange of data withexternal machines (e.g., computing devices of any kind) via a network1726 (e.g., an Ethernet connection, a digital subscriber line (DSL), atelephone line, coaxial cable, a cellular telephone system, etc.).

The processor platform 1700 of the illustrated example also includes oneor more mass storage devices 1728 for storing software and/or data.Examples of such mass storage devices 1728 include flash devices, floppydisk drives, hard drive disks, optical compact disk (CD) drives, opticalBlu-ray disk drives, RAID systems, and optical digital versatile disk(DVD) drives.

Coded instructions 1732 representative of the example machine readableinstructions of FIGS. 10-14 may be stored in the mass storage device1728, in the volatile memory 1714, in the non-volatile memory 1716,and/or on a removable tangible computer readable storage medium such asa CD or DVD.

In the example of FIG. 17, the processor 1712 implements the examplecustom interface 612, etc. In certain examples, as discussed herein, thehardware of processor 1712 is virtualized using virtualization such asVMs and/or containers.

FIG. 18 is a block diagram of an example processor platform 1800structured to execute the instructions of FIGS. 10-14 to implement theexample systems, operation, and management of FIGS. 1-9. The processorplatform 1800 of the illustrated example includes a processor 1812. Theprocessor 1812 of the illustrated example is hardware. For example, theprocessor 1812 can be implemented by one or more integrated circuits,logic circuits, microprocessors or controllers from any desired familyor manufacturer.

The processor 1812 of the illustrated example includes a local memory1813 (e.g., a cache), and executes instructions to implement the examplecloud management platform or system 600 or portions thereof, such as theexample user device 616. The processor 1812 of the illustrated exampleis in communication with a main memory including a volatile memory 1814and a non-volatile memory 1816 via a bus 1818. The volatile memory 1814may be implemented by Synchronous Dynamic Random Access Memory (SDRAM),Dynamic Random Access Memory (DRAM), RAMBUS Dynamic Random Access Memory(RDRAM) and/or any other type of random access memory device. Thenon-volatile memory 1816 may be implemented by flash memory and/or anyother desired type of memory device. Access to the main memory 1814,1816 is controlled by a memory controller.

The processor platform 1800 of the illustrated example also includes aninterface circuit 1820. The interface circuit 1820 may be implemented byany type of interface standard, such as an Ethernet interface, auniversal serial bus (USB), and/or a PCI express interface.

In the illustrated example, one or more input devices 1822 are connectedto the interface circuit 1820. The input device(s) 1822 permit(s) a userto enter data and commands into the processor 1812. The input device(s)can be implemented by, for example, an audio sensor, a microphone, akeyboard, a button, a mouse, a touchscreen, a track-pad, a trackball,isopoint and/or a voice recognition system. In some examples, the inputdevice(s) 1822 are used to implement the tenant administrator workstation 116 (see FIG. 1).

One or more output devices 1824 are also connected to the interfacecircuit 1820 of the illustrated example. The output devices 1824 can beimplemented, for example, by display devices (e.g., a light emittingdiode (LED), an organic light emitting diode (OLED), a liquid crystaldisplay, a cathode ray tube display (CRT), a touchscreen, a tactileoutput device, a printer and/or speakers). The interface circuit 1820 ofthe illustrated example, thus, typically includes a graphics drivercard, a graphics driver chip or a graphics driver processor. In someexamples, the output device(s) 1824 are used to implement the tenantadministrator work station 116 (see FIG. 1).

The interface circuit 1820 of the illustrated example also includes acommunication device such as a transmitter, a receiver, a transceiver, amodem and/or network interface card to facilitate exchange of data withexternal machines (e.g., computing devices of any kind) via a network1826 (e.g., an Ethernet connection, a digital subscriber line (DSL), atelephone line, coaxial cable, a cellular telephone system, etc.).

The processor platform 1800 of the illustrated example also includes oneor more mass storage devices 1828 for storing software and/or data.Examples of such mass storage devices 1828 include flash devices, floppydisk drives, hard drive disks, optical compact disk (CD) drives, opticalBlu-ray disk drives, RAID systems, and optical digital versatile disk(DVD) drives.

Coded instructions 1832 representative of the example machine readableinstructions of FIGS. 10-14 may be stored in the mass storage device1828, in the volatile memory 1814, in the non-volatile memory 1816,and/or on a removable tangible computer readable storage medium such asa CD or DVD.

In the example of FIG. 18, the processor 1812 implements the exampleuser device 616, etc. In certain examples, as discussed herein, thehardware of processor 1812 is virtualized using virtualization such asVMs and/or containers.

From the foregoing, it will be appreciated that the above disclosedmethods, apparatus, and articles of manufacture have been disclosed toregister endpoints and/or associated endpoint adapters with a virtualcloud management platform. The disclosed methods, apparatus and articlesof manufacture improve the operation of a computing device (real and/orvirtual) and management platform by separating endpoints from the corecloud management platform, enabling partners to add endpoints andenabling the cloud management platform to disconnect or delete adaptersto those endpoints without negatively impacting the rest of the system.The disclosed methods, apparatus and articles of manufacture areaccordingly directed to one or more improvement(s) in the functioning ofa computer.

Thus, certain examples improve provisioning of virtual computingresources in an environment, such as a cloud computing environment.Certain examples provide a technical improvement of reverse proxymanagement of endpoints and user devices organized by the cloud platformhost in a central registry/repository. Certain examples enable endpointsto run in sandboxed fashion on a virtual machine or container separatefrom a VM/container hosting the cloud management platform. Thus, thecloud management platform has separation from and control of connectedendpoints to enable/connect and disable/disconnect them throughassociated adapters and can treat external endpoints as internalendpoints through the handshake data exchange and registration with theplatform host and endpoint registry.

Example 1 provides a cloud management system including: a firstinterface to communicate with a second interface external to the cloudmanagement system; and a host to manage requests from the secondinterface and allocate resources to the second interface as a reverseproxy for the second interface with respect to a backend. The host ofexample 1 is to at least: add, at the request of the second interface,an endpoint with respect to the second interface; fetch, at the requestof the second interface, data for the endpoint from the backend, thebackend identified for the endpoint based on metadata in a componentregistry; and provide the data from the backend to the second interface.

Example 2 includes example 1, wherein the cloud management system is amulti-cloud management system.

Example 3 includes example 1, wherein the second interface is tocommunicate with the first interface via an external endpoint.

Example 4 includes example 1, wherein the host is to perform a securitycheck to verify the second interface before fetching the data from thebackend.

Example 5 includes example 1, wherein the second interface and theendpoint are to be instantiated on a separate virtual machine orcontainer from the host.

Example 6 includes example 1, wherein the second interface includes acustom graphical user interface connected to the cloud management systemby the endpoint and enabled by the data provided from the backend viathe host.

Example 7 includes example 1, wherein the component registry is to storemetadata for the backend for the second interface including anidentifier, access credentials, and associated backend services for thesecond interface.

Example 8 provides a non-transitory computer-readable storage mediumcomprising computer readable instructions that, when executed, cause atleast one processor to at least implement a cloud management platform.The cloud management platform of example 8 includes: a first interfaceto communicate with a second interface external to the cloud managementsystem; and a host to manage requests from the second interface andallocate resources to the second interface as a reverse proxy for thesecond interface with respect to a backend. The host of example 8 is toat least: add, at the request of the second interface, an endpoint withrespect to the second interface; fetch, at the request of the secondinterface, data for the endpoint from the backend, the backendidentified for the endpoint based on metadata in a component registry;and provide the data from the backend to the second interface.

Example 9 includes example 8, wherein the cloud management system is amulti-cloud management system.

Example 10 includes example 8, wherein the second interface is tocommunicate with the first interface via an external endpoint.

Example 11 includes example 8, wherein the host is to perform a securitycheck to verify the second interface before fetching the data from thebackend.

Example 12 includes example 8, wherein the second interface and theendpoint are to be instantiated on a separate virtual machine orcontainer from the host.

Example 13 includes example 8, wherein the second interface includes acustom graphical user interface connected to the cloud management systemby the endpoint and enabled by the data provided from the backend viathe host.

Example 14 includes example 8, wherein the component registry is tostore metadata for the backend for the second interface including anidentifier, access credentials, and associated backend services for thesecond interface.

Example 15 provides a method including: communicating, via a firstinterface of a cloud management system by executing an instruction usingat least one processor, with a second interface external to the cloudmanagement system; adding, at the request of the second interface andvia a host of the cloud management system as a reverse proxy for thesecond interface by executing an instruction using the at least oneprocessor, an endpoint with respect to the second interface; fetching,at the request of the second interface and via the host as reverse proxyby executing an instruction using the at least one processor, data forthe endpoint from the backend, the backend identified for the endpointbased on metadata in a component registry; and providing, via the hostby executing an instruction using the at least one processor, the datafrom the backend to the second interface.

Example 16 includes example 15, wherein the second interface is tocommunicate with the first interface via an external endpoint.

Example 17 includes example 15, further including performing a securitycheck to verify the second interface before fetching the data from thebackend.

Example 18 includes example 15, wherein the second interface and theendpoint are to be instantiated on a separate virtual machine orcontainer from the host.

Example 19 includes example 15, wherein the second interface includes acustom graphical user interface connected to the cloud management systemby the endpoint and enabled by the data provided from the backend viathe host.

Example 20 includes example 15, wherein the component registry is tostore metadata for the backend for the second interface including anidentifier, access credentials, and associated backend services for thesecond interface.

Although certain example methods, apparatus and articles of manufacturehave been disclosed herein, the scope of coverage of this patent is notlimited thereto. On the contrary, this patent covers all methods,apparatus and articles of manufacture fairly falling within the scope ofthe claims of this patent.

What is claimed is:
 1. An apparatus comprising: memory to storeinstructions; and processor circuitry to execute the instructions to atleast: register a first endpoint with a registry, the first endpointembedded with the apparatus; register an adapter with the registry, theadapter associated with a second endpoint added to the apparatus;allocate, using the registry, resources of a same type among the firstendpoint and the second endpoint; and provide feedback to the secondendpoint via the adapter.
 2. The apparatus of claim 1, wherein theapparatus includes a cloud management platform.
 3. The apparatus ofclaim 1, wherein the second endpoint is deactivated by removing theadapter from the registry.
 4. The apparatus of claim 1, wherein theadapter is registered using metadata.
 5. The apparatus of claim 4,wherein the metadata includes an identifier, access credentials, andservices associated with the second endpoint.
 6. The apparatus of claim1, wherein the processor circuitry is to start a registration service tocommunicate with the second endpoint via the adapter to register theadapter and the second endpoint.
 7. The apparatus of claim 1, whereinthe processor circuitry is to generate an interface to register theadapter and the second endpoint.
 8. The apparatus of claim 1, whereinthe processor circuitry is to serve as a reverse proxy for the secondendpoint.
 9. The apparatus of claim 1, wherein the first endpoint is tobe instantiated on a first virtual machine and the second endpoint is tobe instantiated on a second virtual machine.
 10. The apparatus of claim1, wherein the resources of the same type include resources internal tothe apparatus.
 11. At least one non-transitory computer-readable storagemedium comprising computer readable instructions that, when executed,cause at least one processor to at least: register a first endpoint witha registry, the first endpoint embedded within a system; register anadapter with the registry, the adapter associated with a second endpointadded to the system; allocate, using the registry, resources of a sametype among the first endpoint and the second endpoint; and providefeedback to the second endpoint via the adapter.
 12. The at least onenon-transitory computer-readable storage medium of claim 11, wherein thesystem is a cloud management system, and wherein the instructions, whenexecuted, cause the at least one processor to register the firstendpoint and the adapter with the registry in the cloud managementsystem.
 13. The at least one non-transitory computer-readable storagemedium of claim 12, wherein the instructions, when executed, cause theat least one processor to deactivate the second endpoint by removing theadapter from the registry.
 14. The at least one non-transitorycomputer-readable storage medium of claim 11, wherein the instructions,when executed, cause the at least one processor to register the adapterusing metadata.
 15. The at least one non-transitory computer-readablestorage medium of claim 11, wherein the instructions, when executed,cause the at least one processor to start a registration service tocommunicate with the second endpoint via the adapter to register theadapter and the second endpoint.
 16. The at least one non-transitorycomputer-readable storage medium of claim 11, wherein the instructions,when executed, cause the at least one processor to generate an interfaceto register the adapter and the second endpoint.
 17. A methodcomprising: registering, by executing an instruction using at least oneprocessor, a first endpoint with a registry, the first endpoint embeddedwithin a system; registering, by executing an instruction using the atleast one processor, an adapter with the registry, the adapterassociated with a second endpoint added to the system; allocating, usingthe registry and by executing an instruction using the at least oneprocessor, resources of a same type among the first endpoint and thesecond endpoint; and providing, by executing an instruction using the atleast one processor, feedback to the second endpoint via the adapter.18. The method of claim 17, wherein the system is a cloud managementsystem, and wherein registering the first endpoint and the adapterincludes registering the first endpoint and the adapter with theregistry in the cloud management system.
 19. The method of claim 18,further including deactivating the second endpoint by removing theadapter from the registry.
 20. The method of claim 17, further includingstarting a registration service to communicate with the second endpointvia the adapter to register the adapter and the second endpoint.
 21. Themethod of claim 17, further including generating an interface toregister the adapter and the second endpoint.